Repository navigation
Fix Ready auto-merge GraphQL client compatibility - #12
Merged
Merged
Conversation
added 9 commits
October 14, 2026 19:03
silveltman
marked this pull request as ready for review
October 14, 2026 18:32
silveltman
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ready auto-merge was failing because Octokit reserves the GraphQL variable name
method. Rename it tomergeMethodfor both the Actions client and the existing release App, preserving the exact-head condition and all required-check gates.The workflow tests now reject reserved transport option names and verify the mutation binding. All 21 tests pass. The README also documents the central workflows and Draft/Ready/production behavior.